-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dry-run and fast-deps behavior testing #12193
Conversation
cc @sbidoul @pradyunsg @uranusjr no rush at all; github doesn't allow me to request reviewers (which is fine). |
913c02f
to
d6e77fb
Compare
d6e77fb
to
1c86633
Compare
08ce2fa
to
700af48
Compare
9c52698
to
700af48
Compare
@pfmoore this is also probably easy to review and merge. |
700af48
to
20b54de
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No real objections to any of this, but there are a few places I wouldn't describe the new code as "clear". That's a matter of opinion, and I'm unlikely to look at these tests very often in future anyway, so I don't want to block the PR because of it, but if it could be simplified/clarified, that would be good.
pip install
behavior testing
pip install
behavior testing
Split out from #12186. In that change, we found that multiple behaviors we expected from
install --dry-run
weren't tested. This change tests that:install --dry-run
is specified.Pip already does these correctly, but now we can be sure.
This also modifies another test (
test_trailing_slash_directory_metadata()
) to avoid using.get_dist()
. This version of the test is more correct and avoids a reliance on.get_dist()
, which will be removed in #12186.